Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

85.130.244.0/23 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=85.130.244.0%2F23"
JSON Docs

Warning: 85.130.244.0/23 is announced by AS208905 (Exelera-AS Exelera Telecom Ltd). 1 warning

Announced as85.130.244.0/23
Origin ASAS208905 Exelera-AS Exelera Telecom Ltd
HolderAS8551-MNT
AllocationRIPE NCC, Israel (IL), allocated 2004-11-24
Size512 addresses
Abuse contactabuse@bezeq.co.il

What to fix

  1. Warning

    Reverse DNS is not delegated for 85.130.244.0/23, so its addresses have no PTR records.

    Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.

    Fix: Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.

    Open in DNS lookup

Checks

Routing and RPKI Announced as 85.130.244.0/23 by AS208905.
  • Pass: Announced as 85.130.244.0/23 by AS208905.
  • Pass: 85.130.244.0/23 from AS208905 is RPKI valid.
  • Pass: 85.130.244.0/24 from AS208905 is RPKI valid. 85.130.244.0/24
  • Pass: 85.130.245.0/24 from AS208905 is RPKI valid. 85.130.245.0/24
  • Pass: Seen by 99% of RIPE RIS peers.
  • Info: The ROA 85.130.244.0/23 AS208905 allows announcements up to /24.
Route85.130.244.0/23
Origin ASAS208905 Exelera-AS Exelera Telecom Ltd RPKI valid
IRR route objectsRIPE
Visibility (RIS peers)318 / 320
First seen2024-05-08
Covering prefixes85.130.240.0/20, 85.130.224.0/19, 85.130.192.0/18
More-specific routes 2
More-specific routeOrigin ASRPKI
85.130.244.0/24 AS208905 RPKI valid
85.130.245.0/24 AS208905 RPKI valid
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
85.130.244.0/23 /24 AS208905
85.130.192.0/18 /24 AS6810

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 85.130.244.0/23, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 85.130.244.0/23, so its addresses have no PTR records.
Reverse zones 2
ZoneNameservers
244.130.85.in-addr.arpa Not delegated
245.130.85.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameTamaras_Business_Customers
Handle85.130.244.0 - 85.130.245.255
Range85.130.244.0 – 85.130.245.255
CountryIL
Statusactive
Registered2024-05-07T14:11:17Z
Last changed2024-05-07T14:11:17Z
Abuse contactabuse@bezeq.co.il
Allocation
Registry (RIR)RIPE NCC
CountryIsrael (IL)
Delegated on2004-11-24
StatusAllocated
Delegated range85.130.128.0/17 (85.130.128.0 – 85.130.255.255)

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant AS8551-MNT
registrant MAINT-AS4148
abuse Abuse-C Role abuse@bezeq.co.il

Source: https://rdap.db.ripe.net/ip/85.130.244.0/23. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB AS208905 is in PeeringDB as Tamares Telecom.
  • Pass: AS208905 is in PeeringDB as Tamares Telecom.
  • Info: Peering policy: Open.
  • Info: Present at 2 internet exchanges with 3 ports (300G in total).
  • Info: The record was last updated 2023-07-06.

About the network that announces this space, so not in the fix list.

NetworkTamares Telecom
AS numberAS208905
TypeNetwork Services, Middle East
Websitehttp://www.tamarestelecom.com
IRR as-setAS-TAMARES-SET
Prefixes (IPv4 / IPv6)0 / 0
Traffic5-10Tbps, Heavy Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2023-07-06
Contacts
Abusenoc@tamarestelecom.com
Maintenancenoc@tamarestelecom.com
Technicalnoc@tamarestelecom.com

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup