Is wehavekids.com down or not working?

What happened to wehavekids.com, why did the website go down and not work? Here you can see who else is having the same problem with wehavekids.com, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, wehavekids.com is working fine, but single failures are possible. If wehavekids.com does not work for you, then report your problem and write a comment.

What to do if the site wehavekids.com is not available? Try our guide.

wehavekids.com outage reports in the last 24 hours

wehavekids.com - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
wehavekids.com
Protocol:
http
Status code:
403
Page size:
0.6 KB
Response time:
0.053sec.
IP:
151.101.66.98
Response headers:
connection: close
content-length: 584
content-type: text/html;charset=utf-8
server: DataDome
x-datadome: protected
accept-ch: Sec-CH-UA,Sec-CH-UA-Mobile,Sec-CH-UA-Platform,Sec-CH-UA-Arch,Sec-CH-UA-Full-Version-List,Sec-CH-UA-Model,Sec-CH-Device-Memory
charset: utf-8
cache-control: max-age=0, private, no-cache, no-store, must-revalidate
pragma: no-cache
access-control-allow-credentials: true
access-control-expose-headers: x-dd-b, x-set-cookie
access-control-allow-origin: *
x-datadome-cid: AHrlqAAAAAMA-DFmzB6cloQABS1HNg==
x-dd-b: 1
set-cookie: datadome=HQpPSYD7y6ADukeQjCJDd9~YMIKsnXf0nFMY47EzF79s_ouPIbzb3B~O9OWK4p9CnxINDhkTIuFc~9rgWUh4PcZwKbx~_XRBFc0an~38aa2_WarVDgdSDcFI9m9S839n; Max-Age=31536000; Domain=.wehavekids.com; Path=/; Secure; SameSite=Lax
x-datadome-devicecheckpassed: NA
x-datadome-traffic-rule-response: block
x-saycdn-ttl: 0.000
accept-ranges: bytes
date: Tue, 01 Oct 2024 07:54:32 GMT
via: 1.1 varnish
x-served-by: cache-ams21074-AMS
x-cache: MISS
x-cache-hits: 0
x-timer: S1727769273.801418,VS0,VE12
strict-transport-security: max-age=31557600
server-timing: time-start-msec;dur=1727769272801,time-elapsed;dur=12,fastly-pop;desc=AMS,hit-state;desc=PASS
DNS records:
A address151.101.130.98
ttl300
A address151.101.2.98
ttl300
A address151.101.194.98
ttl300
A address151.101.66.98
ttl300
NS valuens-686.awsdns-21.net
NS valuens-1334.awsdns-38.org
NS valuens-353.awsdns-44.com
NS valuens-1786.awsdns-31.co.uk
TXT entries_globalsign-domain-verification=gAPFAzHY3-LPxgbcv6Lg4vqINeELTyLzLykq8yFz3t
SOA nsnamens-1334.awsdns-38.org
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with wehavekids.com

Errors on the wehavekids.com website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of wehavekids.com on your own.