Skip to main content
CIDR
/19 · 8.2K IPs
ASN
Servers Tech Fzco
Reverse DNS
ft.com
Last scanned 13 hr ago
Blocklisted
Checking…
Scanning blocklists

Reputation · trust score

A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.

85/100
Trusted
How this score is built

Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →

DNS records

Reverse DNS (PTR)
ft.com
Forward-confirmed (FCrDNS)
Not checked
PTR TTL
600 s
Reverse DNS last checked
2026-10-07 02:44 UTC
Forward DNS last checked
2026-10-07 02:44 UTC

Forward DNS records for ft.com

TypeValuePriorityTTL
A 13.35.107.124 — 60s
A 13.35.107.39 — 60s
A 13.35.107.5 — 60s
A 13.35.107.75 — 60s
A 151.101.130.46 — 3600s
A 151.101.194.46 — 3600s
A 151.101.2.46 — 3600s
A 151.101.66.46 — 3600s
A 3.163.175.17 — 60s
A 3.163.175.39 — 60s
A 3.163.175.53 — 60s
A 3.163.175.54 — 60s
MX alt1.aspmx.l.google.com 20 —
MX alt2.aspmx.l.google.com 20 —
MX alt3.aspmx.l.google.com 30 —
MX alt4.aspmx.l.google.com 30 —
MX aspmx.l.google.com 10 —
NS ns-1447.awsdns-52.org — —
NS ns-1984.awsdns-56.co.uk — —
NS ns-52.awsdns-06.com — —
NS ns-530.awsdns-02.net — —
TXT /9JIaeVTZTKIvRQN3nbfJN6BNbLYOjQelBjl6qUN4/s= — —
TXT IktKRV0FPEeiosHW0zf4Lw — —
TXT MS=ms15735648 — —
TXT MS=ms23088425 — —
TXT MS=ms23619679 — —
TXT MS=ms39959132 — —
TXT MS=ms50570352 — —
TXT MS=ms54676079 — —
TXT MS=ms87193117 — —
TXT access-domain-verification=436fdc74c8ebd0d982301a0c1a3b752176a55246a7c97b159d335f195ea09288 — —
TXT adobe-idp-site-verification=c5baff41-b308-42c8-8ace-9393ace1d783 — —
TXT amazonses:Dw3ndQPO42StK7/Toh+RBHUOydpp514RsYbCJWony5A= — —
TXT amazonses:HvBZtqew7lgZbGfdU4V/Gd07PT9PXZUEHTkH5eHdwYw= — —
TXT amazonses:NceEuFJaVFhkB7aKpzAp27vTpU0Z/HHD/LBjG/Jg9yk= — —
TXT apple-domain-verification=hiRNMTWYN1yBRwg4 — —
TXT asv=d0c9c01ad65bddcc0eee60ecfc13201f — —
TXT atlassian-domain-verification=/flKBbAdKfXx7mblo5+qFf5hD7psLK8FrrnR9vB5xL5zyvD19GRnuo4/PrNPij84 — —
TXT atlassian-domain-verification=hVzdk0lf3NQ/udMQWFZWxWA8eOjXyOjGD6e+1kcBpqqsLX8LHdqE5pNv+c32u0ho — —
TXT cloudflare_dashboard_sso=cb52a8597e3ed22ef489d879b270709f — —
TXT docusign=c04c5b8c-58c7-4024-99f3-fb1f636da0d0 — —
TXT facebook-domain-verification=15ore8k5t6ft96p6lt8sb02m8dls4w — —
TXT facebook-domain-verification=k64kwvkb345rz292m21kltvaf1r5d5 — —
TXT facebook-domain-verification=k7y14n0l2qtawyedyyz5fiu9ngsvg7 — —
TXT facebook-domain-verification=wb6970zko03f90a0lxi4gpt89lnybl — —
TXT facebook-domain-verification=wnuqdndij8zjroogp6jlsu8ud0yu3q — —
TXT figma-domain-verification=8ea20ad3e142b70da670a8313afdeb991a189ec78f024825dd321a4f186a9dc7-1762176141 — —
TXT google-site-verification=nqX1TPP8SIFG3F_1ULz5qPw7qEqO4Bowh14fkxdESfo — —
TXT google-site-verification=sXoPNkEqXt3ce7rT9MnH2bnjNLKFR3oizWMMmkQFDLI — —
TXT jamf-site-verification=lbgmfPGJwTYfXRt8qeKWNA — —
TXT make-domain-verification=25fb721f-943e-4b5d-8268-48ff60f61191 — —
TXT mandrill_verify.JufTb8PUBLcJ8tPLkojezA — —
TXT mongodb-site-verification=l2ACYeoZMEwgZw4T5SPbJiGRPoBKC3wt — —
TXT notion-domain-verification=mkIjxnyKOdeLmDtzKbgWoLKngPBDT5U2dmxXWbCzf7l — —
TXT openai-domain-verification=dv-bxQol3maMz9EffWDUvCsa5cG — —
TXT pardot596911=26c4369191477541d69fe3837196409e805f282f3e4aef8171e20293d42957ad — —
TXT pardot_218412=760e83e8fe2a693cf55ad39557c5d2ffa643883ebace2abcb9c1ce7397544cb0 — —
TXT slack-domain-verification=z853Xxvh1FXWNfobsGsdZp626tQCj0k4tvSa2w4O — —
TXT sophos-domain-verification=67ec68273fd952a93f6de23473f7209d3f10f79602e68759b4a0fbf41588d36b — —
TXT v=spf1 include:_spf.google.com include:mktomail.com include:_spf.salesforce.com include:email.hivebrite.com include:spf.mandrillapp.com include:24982124.spf07.hubspotemail.net include:spf.alida.io -all — —
CAA iodef mailto:cyber.security@ft.com 0 —
CAA issue amazon.com 0 —
CAA issue certainly.com 0 —
CAA issue digicert.com 0 —
CAA issue globalsign.com 0 —
CAA issue letsencrypt.org 0 —
CAA issue pki.goog; cansignhttpexchanges=yes 0 —
CAA issuewild amazon.com 0 —
CAA issuewild certainly.com 0 —
CAA issuewild digicert.com 0 —
CAA issuewild letsencrypt.org 0 —
CAA issuewild pki.goog; cansignhttpexchanges=yes 0 —
every IP & sub-domain we've seen under this domain

Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.

Domains hosted

as of 2026-10-04 UTC

0

issued.live saw no domain resolving to this IP in its latest weekly snapshot.

Domain data provided by issued.live — for full details visit https://issued.live/pricing

Reverse DNS history

How this IP's reverse DNS (PTR) has changed over time, from our scans.

  1. ft.com stable — Jul 10, 2026 → present 1 brief no-PTR dropout

Network Allocation for 144.124.247.83

CIDR range
144.124.224.0/19
IP range (int)
2,424,102,912 — 2,424,111,103
Prefix length
/19
Organization
Servers Tech Fzco
ASN
AS216071
ASN name
Servers Tech Fzco
Location
Amsterdam, North Holland, The Netherlands
Coordinates
52.371600, 4.888300
Accuracy radius
20 km
Postal code
1012
Regional Internet Registry
RIPE
Allocated
1990-12-01
Data source(s)
maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
Last updated
2026-10-07 08:47:28

Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.

Announced prefix
Origin AS
Announcement samples
26,543
Last seen
2026-10-07 16:34:22

RIR Ownership History

Atom feed ⇲

Allocation changes captured from regional internet registry (RIR) delegation files, re-imported every six hours, for ranges that have contained this IP.

Date Event From To
2026-05-10 RIR Transfer arin ripe
2026-05-10 Country Change NL AE

See the full history for 144.124.224.0/19.

Frequently Asked Questions

Who owns 144.124.247.83?

144.124.247.83 is allocated to Servers Tech Fzco (AS216071), registered in Amsterdam, The Netherlands.

Where is 144.124.247.83 located?

The geolocation for 144.124.247.83 maps to Amsterdam, The Netherlands based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.

What network is 144.124.247.83 on?

144.124.247.83 belongs to the 144.124.224.0/19 network block announced by AS216071. This range contains 8,192 addresses.

Does 144.124.247.83 have a reverse DNS record?

Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.

Neighbors

Other addresses in the same /24.

Related

Last updated: 2026-10-07 13:19:43 UTC
Share